Graphical user interfaces for facilitating end-to-end transactions on computing devices

ABSTRACT

Methods and systems for facilitating group payment are disclosed. In one embodiment, a group payment system is configured to execute instructions to perform operations that include receiving, from a first computing device, a request to create a group payment event and, in response, providing to the first computing device a first interface associated with the group payment event. The operations further include receiving, from a second computing device, a request to join the group payment event and, in response, providing a second interface to the second computing device. The operations further include receiving, from the first and/or second computing devices, messages associated with the group payment event and modifying the first and second interfaces to display the messages. The operations further include receiving, from the first and/or second computing devices, financial contributions for the group payment event and modifying the first and second interfaces to display the financial contributions.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/262,693 filed Dec. 3, 2015, the contents of which are herebyincorporated in their entirety.

BACKGROUND

Existing applications available on computing devices permit users toexchange payment. For example, applications such as PayPal™ and GoogleWallet™ are configured to provide graphical user interfaces throughwhich a user can make a payment to or request a payment from anotheruser. However, existing graphical user interfaces on mobile devices areinflexible and unable to adapt to subsequent changes in a user's paymentor request for payment. Moreover, existing applications on computingdevices are ill-equipped to facilitate payment among multiple users.Lastly, existing applications graphical user interfaces on mobiledevices are unable to provide graphical user interfaces through which,in addition to making and requesting payment, multiple users may engagein discussion regarding such payments. Accordingly, mobile applicationsoffering improved graphical user interfaces are desired.

SUMMARY

The disclosed embodiments may include systems and methods forfacilitating group payment.

In one embodiment, a group payment system is disclosed. The grouppayment system may comprise a communication device configured tocommunicate with a plurality of computing devices, a memory storinginstructions, and a processor configured to execute the instructions toperform operations. The operations may comprise receiving, from a firstcomputing device in the plurality of computing devices, a request tocreate a group payment event and, in response to receiving the requestto create the group payment event, providing to the first computingdevice a first interface associated with the group payment event. Theoperations may further comprise receiving, from at least a secondcomputing device in the plurality of computing devices, a request tojoin the group payment event and, in response to receiving the requestto join the group payment event, providing a second interface to atleast the second computing device. The operations may further comprisereceiving, from at least one of the first computing device and thesecond computing device, a plurality of messages associated with thegroup payment event and, in response to receiving each message in theplurality of messages, modifying the first interface and secondinterface to display the message. The operations may still furthercomprise receiving, from at least one of the first computing device andthe second computing device, a specification of financial contributionsfor the group payment event and, in response to receiving thespecification of the financial contributions, modifying the firstinterface and second interface to display the specification of thefinancial contributions.

In another embodiment, a method is disclosed. The method may comprisereceiving, from a first computing device in the plurality of computingdevices, a request to create a group payment event and, in response toreceiving the request to create the group payment event, providing tothe first computing device a first interface associated with the grouppayment event. The method may further comprise receiving, from at leasta second computing device in the plurality of computing devices, arequest to join the group payment event and, in response to receivingthe request to join the group payment event, providing a secondinterface to at least the second computing device. The method mayfurther comprise receiving, from at least one of the first computingdevice and the second computing device, a plurality of messagesassociated with the group payment event and, in response to receivingeach message in the plurality of messages, modifying the first interfaceand second interface to display the message. The method may stillfurther comprise receiving, from at least one of the first computingdevice and the second computing device, a specification of financialcontributions for the group payment event and, in response to receivingthe specification of the financial contributions, modifying the firstinterface and second interface to display the specification of thefinancial contributions.

In another embodiment, a computing device is disclosed. The computingdevice may comprise a communication device configured to communicatewith a group payment system, an input device, a display device, a memorystoring instructions, and a processor configured to execute theinstructions to perform operations. The operations may comprisereceiving, via the input device, a request to create a group paymentevent, electronically transmitting the request to the group paymentsystem, and receiving from the group payment system an interfaceassociated with the group payment event for display on the displayingdevice. The operations may further comprise receiving, via the inputdevice, a first message associated with the group payment event,electronically transmitting the first message to the group paymentsystem and modifying the interface to display the first message, andreceiving from the group payment system a second message and modifyingthe interface to display the second message. The operations may furthercomprise receiving, via the input device, a specification of financialcontributions for the group payment event and, in response to receivingthe specification of the financial contributions, electronicallytransmitting the specification of the financial contributions to thegroup payment system and modifying the interface to display thespecification of the financial contributions.

Aspects of the disclosed embodiments may include tangiblecomputer-readable media that store software instructions that, whenexecuted by one or more processors, are configured for and capable ofperforming and executing one or more of the methods, operations, and thelike consistent with the disclosed embodiments. Also, aspects of thedisclosed embodiments may be performed by one or more processors thatare configured as special-purpose processor(s) based on softwareinstructions that are programmed with logic and instructions thatperform, when executed, one or more operations consistent with thedisclosed embodiments.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1 is a block diagram of an exemplary system, consistent withdisclosed embodiments.

FIG. 2 is a block diagram of an exemplary group payment system,consistent with disclosed embodiments.

FIG. 3 is a block diagram of an exemplary computing device, consistentwith disclosed embodiments.

FIG. 4 is a flowchart of an exemplary group payment process, consistentwith disclosed embodiments.

FIG. 5 is a flowchart of another exemplary group payment process,consistent with disclosed embodiments.

FIGS. 6A-K illustrate exemplary interfaces on computing devices,consistent with disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to the disclosed embodiments,examples of which are illustrated in the accompanying drawings.

Disclosed are graphical user interfaces that permit multiple users toflexibly discuss, coordinate, and continually revise paymentarrangements among the users. Unlike existing graphical user interfaces,which are inflexible and unable to adapt to subsequent changes in auser's payment or request for payment, the disclosed graphical userinterfaces are configured to be updated to reflect subsequent purchasetransactions, changed financial contributions, and/or other informationimpacting payments and/or requests for payment among users. Moreover,whereas existing applications on computing devices are ill-equipped tofacilitate payment among multiple users, the disclosed graphical userinterfaces are configured to be provided to multiple computing devices,permitting multiple users to record purchase transactions, changefinancial contributions, and make or request payments. Lastly, whileexisting applications graphical user interfaces are unable to providegraphical user interfaces through which, in addition to making andrequesting payment, multiple users may engage in discussion regardingsuch payments, the disclosed graphical user interfaces are configured tointerface with multiple computing devices to receive messages in orderto update the graphical user interfaces to reflect messages frommultiple users.

FIG. 1 is a block diagram of an exemplary system 100, consistent withdisclosed embodiments. In particular, system 100 may be configured forperforming one or more operations consistent with the disclosedembodiments. In one embodiment, system 100 may include a computingdevice 102 associated with a user 104, a computing device 106 associatedwith a user 108, a computing device 110 associated with a user 112, agroup payment system 114, a financial service provider (FSP) system 116,and third-party system(s) 118, all of which may be communicativelycoupled by a network 120.

While three computing devices 102, 106, 110 and users 104, 108, 112 areshown, it will be understood that system 100 may include more or fewercomputing devices. Further, while only group payment system 114, FSPsystem 116, and network 120 are shown, it will be understood that system100 may include more than one of any of these components. Still further,while multiple third-party systems 118 are shown, it will be understoodthat system 100 may include only one third-party system 118 as well. Thecomponents and arrangement of the components included in system 100 mayvary. Thus, system 100 may include other components that perform orassist in the performance of one or more processes consistent with thedisclosed embodiments.

Group payment system 114 may be configured to facilitate a group paymentevent for users 104, 108, and 112. To this end, users 104, 108, and 112may access group payment system 114 using their respective computingdevices 102, 106, and 110. For example, computing devices 102, 106, and110 may be configured to execute a mobile application provided by grouppayment system 114. Group payment system 114 may facilitate the grouppayment event by, for example, providing particular interfaces tocomputing devices 102, 106, and 110, thereby enabling users 104, 108,and 112 to create the group payment event, invite others to join thegroup payment event, discuss the group payment event, and/or specifyrespective financial contributions for the group payment event. Grouppayment system 114 may facilitate the group payment event in othermanners as well, as discussed below. Group payment system 114 is furtherdescribed below in connection with FIG. 2. Computing devices 102, 106,and 110 are further described below in connection with FIG. 3.

As shown, computing devices 102, 106, and 110 and group payment system114 may be communicatively coupled to FSP system 116 over network 120.FSP system 116 may be associated with a financial service entity thatprovides, maintains, manages, or otherwise offers financial services.For example, the financial service entity may be a bank, credit cardissuer, or any other type of financial service entity that generates,provides, manages, and/or maintains financial service accounts for oneor more customers. Financial service accounts may include, for example,credit card accounts, loan accounts, checking accounts, savingsaccounts, reward or loyalty program accounts, and/or any other type offinancial service account known to those skilled in the art. Financialservice accounts may be associated with one or more currencies, digitalassets (e.g., Bitcoin™), and/or any other type of financial currency.

FSP system 116 may be one or more computing devices configured toperform one or more operations consistent with maintaining financialservice accounts, including a financial service account associated withusers 104, 108, and/or 112. FSP system 116 may be further configured togenerate content for a display device included in, or connected to,computing devices 102, 106, and/or 110. For example, FSP system 116 mayprovide content through a mobile banking application on computingdevices 102, 106, and/or 110. Alternatively or additionally, FSP system116 may provide content through one or more web sites or online portalsthat are accessible by computing devices 102, 106, and/or 110 overnetwork 120. FSP system 116 may be one or more computing devices furtherconfigured to authenticate financial transactions associated withfinancial service accounts. In particular, FSP system 116 may beconfigured to authenticate financial transactions associated with users'104, 108, and/or 112 financial service account(s). The disclosedembodiments are not limited to any particular configuration of FSPsystem 116.

As shown, computing devices 102, 106, and 110 and group payment system114 may additionally be communicatively coupled to one or morethird-party system(s) 118 over network 120. Third-party systems 118 mayinclude one or more computing systems configured to perform one or moreoperations consistent with facilitating electronic payment between users104, 108, and/or 112. To this end, third-party systems 118 may beconfigured to execute instructions to perform one or more processesfacilitating the electronic transfer of funds between financial serviceaccounts associated with users 104, 108, and/or 112. This may occur as adirect transfer (within the same institution) or a Wire Transfer. Insome embodiments, the third-party system(s) 118 may include a systemsimilar to, for example, PayPal™, Google Wallet™, Dwolla™, orblockchain. Alternatively or in addition, a “bill pay” account may beused to transfer money via ACH or a paper check. Still alternatively orin addition, third-party system(s) 118 may facilitate payment using oneor more electronic tokens, e.g., information items that point tofinancial service accounts without using highly sensitive accountinformation. Third-party system(s) 118 may take other forms as well, andthe disclosed embodiments are not limited to any particularconfiguration of third-party system(s) 118.

While group payment system 114, FSP system 116, and third-partysystem(s) 118 are shown separately, in some embodiments group paymentsystem 114 may include or be otherwise related to one or both of FSPsystem 116 and third-party system(s) 118. For example, in someembodiments the facility of third-party system(s) 118 may be providedinstead by one or both of group payment system 114 and FSP system 116.As another example, in some embodiments the facility of both FSP system116 and third-party system(s) 118 may be provided by group paymentsystem 114. Other examples are possible as well.

Network 120 may be any type of network configured to providecommunication between components of system 100. For example, network 120may be any type of network (including infrastructure) that providescommunications, exchanges information, and/or facilitates the exchangeof information, such as the Internet, a Local Area Network, near fieldcommunication (NFC), optical code scanner, or other suitableconnection(s) that enables the sending and receiving of informationbetween the components of system 100. In other embodiments, one or morecomponents of system 100 may communicate directly through a dedicatedcommunication link(s).

It is to be understood that the configuration and boundaries of thefunctional building blocks of system 100 have been defined herein forthe convenience of the description. Alternative boundaries can bedefined so long as the specified functions and relationships thereof areappropriately performed. Alternatives (including equivalents,extensions, variations, deviations, etc., of those described herein)will be apparent to persons skilled in the relevant art(s) based on theteachings contained herein. Such alternatives fall within the scope andspirit of the disclosed embodiments.

FIG. 2 is a block diagram of an exemplary group payment system 200,consistent with disclosed embodiments. As shown, group payment system200 may include a communication device 202, one or more processor(s)204, and a memory 206 including one or more programs 208 and data 210.

In some embodiments, group payment system 200 may take the form of aserver, general purpose computer, mainframe computer, or any combinationof these components. Other implementations consistent with disclosedembodiments are possible as well.

Communication device 202 may be configured to communicate with one ormore computing devices, such as computing devices 102, 106, and 110described above. In some embodiments, communication device 202 may beconfigured to communicate with one or more FSP systems, such as FSPsystem 116 described above, and/or third-party system(s), such asthird-party system(s) 118 described above. Communication device 202 maybe configured to communicate with other components as well.

Communication device 202 may be configured to provide communication overa network, such as network 120 described above. To this end,communication device 202 may include, for example, one or more digitaland/or analog devices that allow group payment system 200 to communicatewith and/or detect other components, such as a network controller and/orwireless adaptor for communicating over the Internet. Otherimplementations consistent with disclosed embodiments are possible aswell.

Processor(s) 204 may include one or more known processing devices, suchas a microprocessor from the Pentium™ or Xeon™ family manufactured byIntel™, the Turion™ family manufactured by AMD™, the “Ax” or “Sx” familymanufactured by Apple™, or any of various processors manufactured by SunMicrosystems, for example. The disclosed embodiments are not limited toany type of processor(s) otherwise configured to meet the computingdemands required of different components of group payment system 200.

Memory 206 may include one or more storage devices configured to storeinstructions used by processor(s) 204 to perform functions related todisclosed embodiments. For example, memory 206 may be configured withone or more software instructions, such as program(s) 208, that mayperform one or more operations when executed by processor(s) 204. Thedisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, memory 206 mayinclude a single program 208 that performs the functions of grouppayment system 200, or a plurality of program 208. Memory 206 may alsostore data 210 that is used by program(s) 208.

In certain embodiments, memory 206 may store sets of instructions forcarrying out the processes described below in connection with FIG. 4.Other instructions are possible as well. In general, instructions may beexecuted by processor(s) 204 to perform one or more processes consistentwith disclosed embodiments.

The components of group payment system 200 may be implemented inhardware, software, or a combination of both hardware and software, aswill be apparent to those skilled in the art. For example, although oneor more components of group payment system 200 may be implemented ascomputer processing instructions, all or a portion of the functionalityof group payment system 200 may be implemented instead in dedicatedelectronics hardware.

Group payment system 200 may also be communicatively connected to one ormore database(s) 212. In one aspect, group payment system 200 mayinclude database(s) 212. Alternatively, database(s) 212 may be locatedremotely from group payment system 200. Group payment system 200 may becommunicatively connected to database(s) 212 through a network, such asnetwork 120 described above. Database(s) 212 may include one or morememory devices that store information and are accessed and/or managedthrough group payment system 200. By way of example, database(s) 212 mayinclude Oracle™ databases, Sybase™ databases, or other relationaldatabases or non-relational databases, such as Hadoop® sequence files,HBase™, or Cassandra™. Database(s) 212 may include computing components(e.g., database management system, database server, etc.) configured toreceive and process requests for data stored in memory devices ofdatabase(s) 212 and to provide data from database(s) 212.

FIG. 3 is a block diagram of an exemplary computing device 300,consistent with disclosed embodiments. As shown, computing device 300includes a communication device 302, an input device 304, a display 306,processor(s) 308, and a memory 310 including program(s) 312 and data314.

In some embodiments, computing device 300 may take the form of a mobilecomputing device, such as a smartphone, tablet, laptop computer, or anycombination of these components. Alternatively, computing device 300 maybe configured as any wearable item, including jewelry, smart glasses, orany other device suitable for carrying or wearing on a customer'sperson. Still alternatively, computing device 300 may be configured as adesktop computer. Other implementations consistent with disclosedembodiments are possible as well.

Communication device 302 may be configured to communicate with a grouppayment system, such as group payment systems 114 and 200 describedabove. In some embodiments, communication device 302 may be furtherconfigured to communicate with one or more FSP systems, such as FSPsystem 116 described above, and/or third-party system(s), such asthird-party system(s) 118 described above. Communication device 302 maybe configured to communicate with other components as well.

Communication device 302 may be configured to provide communication overa network, such as network 120 described above. To this end,communication device 302 may include, for example, one or more digitaland/or analog devices that allow computing device 300 to communicatewith and/or detect other components, such as a network controller and/orwireless adaptor for communicating over the Internet. Otherimplementations consistent with disclosed embodiments are possible aswell.

Input device 304 may be configured to receive input from a user. Inparticular, input device 304 may be configured to receive one or more ofrequests to create group payment events, messages associated with grouppayment events, and specifications of financial contributions for grouppayment events. Input device 304 may be configured to receive otherinformation as well. Input device 304 may take the form of, for example,a touch-sensitive area, a keyboard, buttons, or microphones. Other inputdevices are possible as well. The disclosed embodiments are not limitedto any type of input devices otherwise configured to receive input froma user.

Display device 306 may be any display device configured to displayinterfaces on computing device 300. In some embodiments, display device306 may include a screen for displaying a graphical and/or text-baseduser interface, including but not limited to, liquid crystal displays(LCD), light emitting diode (LED) screens, organic light emitting diode(OLED) screens, and other known display devices. In some embodiments,display device 306 may also include one or more digital and/or analogdevices that allow a user to interact with computing device 300, such asa touch-sensitive area, a keyboard, buttons, or microphones. In someembodiments, display device 306 may be implemented together with inputdevice 304. Other display devices are possible as well. The disclosedembodiments are not limited to any type of display devices otherwiseconfigured to display interfaces.

Processor(s) 308 may include one or more known processing devices, suchas a microprocessor from the Pentium™ or Xeon™ family manufactured byIntel™, the Turion™ family manufactured by AMD™, the “Ax” or “Sx” familymanufactured by Apple™, or any of various processors manufactured by SunMicrosystems, for example. Processor(s) 308 may also include variousarchitectures (e.g., x86 processor, ARM®, etc.). The disclosedembodiments are not limited to any type of processor(s) otherwiseconfigured to meet the computing demands required of differentcomponents of computing device 300.

Memory 310 may include one or more storage devices configured to storeinstructions used by processor(s) 308 to perform functions related todisclosed embodiments. For example, memory 310 may be configured withone or more software instructions, such as program(s) 312, that mayperform one or more operations when executed by processor(s) 308. Thedisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, memory 310 mayinclude a single program 312 that performs the functions of computingdevice 300, or program(s) 312 may comprise multiple programs. Memory 310may also store data 314 that is used by program(s) 312.

In certain embodiments, memory 310 may store sets of instructions forcarrying out the processes described below in connection with FIG. 5.Further, in some embodiments, memory 310 may store instructions forexecuting one or more mobile applications. The mobile applications mayinclude, for example, a group payment application that provides grouppayment services offered by a group payment server, such as grouppayment servers 114 and 200 described above. The mobile applications mayfurther include, for example, a mobile banking application for providingfinancial service-related functions offered by an FSP system, such asFSP system 116. These functions may include, for instance, checkingbalances, paying bills, performing financial transactions, budgeting,receiving marketing messages, etc. Other mobile applications arepossible as well. In general, instructions may be executed byprocessor(s) 308 to perform one or more processes consistent withdisclosed embodiments.

The components of computing device 300 may be implemented in hardware,software, or a combination of both hardware and software, as will beapparent to those skilled in the art. For example, although one or morecomponents of computing device 300 may be implemented as computerprocessing instructions, all or a portion of the functionality ofcomputing device 300 may be implemented instead in dedicated electronicshardware.

FIG. 4 is a flowchart of an exemplary group payment process 400,consistent with disclosed embodiments. Group payment process 400 may becarried out at a group payment system, such as group payment systems 114and 200 described above.

As shown in FIG. 4, the group payment process 400 may begin at step 402with a group payment system receiving, from a first computing device ina plurality of computing devices, a request to create a group paymentevent. The first computing device may, for example, have received therequest from a user of the first computing device and transmitted therequest to the group payment system. The group payment system mayreceive the request through, for example, a communication device, suchas communication device 202 described above.

The request may include, for example, a name of the group payment event,a date of the group payment event, a budget for the group payment event,and/or a list of guests. In response to receiving the request, the grouppayment system may configure a group payment event, associating thereceived information with the group payment event. In some embodiments,the group payment system may send invitations to guests included in thelist of guests. For example, the group payment system may send a link(e.g., hyperlink, API, etc.) to a computing device associated with eachguest, inviting the guest to join the group payment event, such as byclicking the link. The group payment system may configure the grouppayment event in other manners as well.

The group payment process 400 continues at step 404 where, in responseto receiving the request to create the group payment event, the grouppayment system provides to the first computing device an interfaceassociated with the group payment event. The group payment system mayprovide the interface through, for example, a communication device, suchas communication device 202 described above. The interface may include,for example, the information received with the request to create thegroup payment event. The interface may include other information aswell.

The first computing device may display the interface. In someembodiments, the interface maybe, for instance, an interface associatedwith a mobile application executing on the first computing device. Otherinterfaces are possible as well.

At step 406, the group payment system receives, from at least a secondcomputing device in the plurality of computing devices, a request tojoin the group payment event. The group payment system may receive therequest through, for example, a communication device, such ascommunication device 202 described above. The second computing devicemay, for example, have received the request from a user of the secondcomputing device and transmitted the request to the group paymentsystem.

In some embodiments, a user associated with the second computing devicemay have been listed as a guest on a guest list received with therequest to create the group payment event, and the second computingdevice may have received a link (e.g., hyperlink, API, etc.) invitingthe second computing device to join the group payment event. In theseembodiments. In these embodiments, the request to join the group paymentevent may comprise a user operating the second computing device to clickon the link provided to the second computing device. In otherembodiments, the second computing device may send the request withoutreceiving an invitation from the group payment system, such as where auser of the first computing device verbally or otherwise invites theuser of the second computing device. The request may be received inother manners as well.

The group payment process continues at step 408 where, in response toreceiving the request to join the group payment event, the group paymentsystem provides the interface to at least the second computing device.The group payment system may provide the interface through, for example,a communication device, such as communication device 202 describedabove. The interface may include, for example, the information receivedwith the request to create the group payment event and/or an indicationof the user associated with the first computing device. The interfacemay include other information as well. Additionally, in someembodiments, the group payment system may provide the interface to othercomputing devices in the plurality of computing devices as well.

The second computing device may display the interface. In someembodiments, the interface may be, for instance, an interface associatedwith a mobile application executing on the second computing device.Other interfaces are possible as well.

At step 410, the group payment system receives, from at least one of thefirst computing device and the second computing device, a plurality ofmessages associated with the group payment event. The group paymentsystem may receive the message(s) through, for example, a communicationdevice, such as communication device 202 described above. The firstand/or second computing device may, for example, have received one ormore messages from a user of the computing device and transmitted themessage(s) to the group payment system.

The messages may enable users of the computing devices to communicateregarding the group payment event. In particular, the users may discussany aspect of the group payment event, such as the guest list, thebudget, and/or financial contributions for the group payment event.Other messages are possible as well. In particular, the content of themessages is not limited to the group payment event.

The process 400 continues at step 412 where, in response to receivingeach message in the plurality of messages, the group payment systemmodifies the interface to display the message. The group payment systemmay provide the modified interface to the plurality of computing devicesthrough, for example, a communication device, such as communicationdevice 202 described above. The plurality of computing devices maydisplay the modified interface. In some embodiments, the group paymentsystem may modify the interface to display the entirety of the message.In other embodiments, the group payment system may modify the interfaceto provide some of, or an indication of, the message, and a user mayinteract with the interface at a computing device to view the messages.The interface may, for example, display the messages in a message streamformat, in which messages appear chronologically. Other arrangements ofmessages in the interface are possible as well.

At step 414, the group payment system receives, from at least one of thefirst computing device and the second computing device, a specificationof financial contributions for the group payment event. The grouppayment system may receive the specification through, for example, acommunication device, such as communication device 202 described above.The specification may indicate, for example, how much each userassociated with a computing device will contribute to the group paymentevent. In some embodiments, the specification may reflect discussionsfacilitated by the messages. The specification of the financialcontributions may be provided as dollar amounts, goods or services,and/or percentages. Other specifications are possible as well.

The process 400 continues at step 416 where, in response to receivingthe specification of the financial contributions, the group paymentserver modifies the interface to display the specification of thefinancial contributions. The group payment system may provide themodified interface to the computing devices through, for example, acommunication device, such as communication device 202 described above.The plurality of computing devices may display the modified interface.The specification may be displayed using text and/or graphics, and thefinancial contributions may be listed as, for example, dollar amounts,goods or services, and/or percentages. The specification may bedisplayed in other manners as well.

FIG. 5 is a flowchart of another exemplary group payment process 500,consistent with disclosed embodiments. Group payment process 500 may becarried out at a computing device, such as computing devices 102, 106,110 and 300 described above.

As shown in FIG. 5, process 500 begins at step 502 with the computingdevice receiving, via an input device, a request to create a grouppayment event. The input device may be, for example, input device 304described above. The computing device may receive the request from, forexample, a user associated with the computing device. The requestmay/include, for example, a name of the group payment event, a date ofthe group payment event, a budget for the group payment event, and/or alist of guests. The request may include other information as well.

At step 504, the computing device electronically transmits the requestto the group payment system. In some embodiments, the computing devicemay electronically transmit the request through a communication device,such as communication device 302, as described above. The group paymentsystem may be, for example, one of group payment systems 114 and 200described above. The group payment system, in response to receiving therequest, may configure the group payment event.

Process 500 continues at step 506 where, in response to transmitting therequest, the computing device receives from the group payment system aninterface associated with the group payment event and displays theinterface. In some embodiments, the computing device may receive theinterface through a communication device, such as communication device302, as described above. The interface may include, for example, theinformation received with the request to create the group payment event.The interface may include other information as well.

The computing device may display the interface through, for example, adisplay device of the computing device, such as display device 306described above. In some embodiments, the interface may be, forinstance, an interface associated with a mobile application executing onthe computing device. Other interfaces are possible as well.

At step 508, the computing device may receive, via the input device, afirst message associated with the group payment event. The message maybe received from, for example, a user associated with the group paymentevent. In some embodiments, the message may be received through, forinstance, a mobile application executing on the computing device. Thefirst message may, for example, be directed to the group payment event.In particular, the first message may discuss any aspect of the grouppayment event, such as the guest list, the budget, and/or financialcontributions for the group payment event. Other messages are possibleas well.

Process 500 continues at step 510 where, in response to receiving thefirst message, the computing device electronically transmits the firstmessage to the group payment system and modifies the interface todisplay the first message. In some embodiments, the computing device mayelectronically transmit the first message through a communicationdevice, such as communication device 302, as described above. In someembodiments, the computing device may display the entirety of the firstmessage. In other embodiments, the computing device may provide some of,or an indication of, the message, and the user associated with thecomputing device may interact with the interface to view the messages.The interface may, for example, display the messages in a message streamformat, in which messages appear chronologically. Other arrangements ofmessages in the interface are possible as well.

At step 512, the computing device receives from the group payment systema second message and modifies the interface to display the secondmessage. The second message may, for example, have been provided by anadditional user associated with an additional computing device. Inparticular, the additional computing device may have received the secondmessage from the additional user and electronically transmitted thesecond message to the group payment server. The group payment server mayhave provided the second message to the computing device in the form ofthe modified interface. The second message may take other forms as well.

At step 514, the computing device receives, via the input device, aspecification of financial contributions for the group payment event.The specification may indicate, for example, how much each user includedin the group payment event will contribute to the group payment event.In some embodiments, the specification may reflect discussions amongusers facilitated by the messages. The specification of the financialcontributions may be provided as dollar amounts, goods or services,and/or percentages. Other specifications are possible as well.

Process 500 continues at step 516 where, in response to receiving thespecification of the financial contributions, the computing deviceelectronically transmits the specification of the financialcontributions to modify the interface to display the specification ofthe financial contributions. In some embodiments, the computing devicemay electronically transmit the specification through a communicationdevice, such as communication device 302, as described above.

The specification may be displayed using text and/or graphics, and thefinancial contributions may be listed as, for example, dollar amounts,goods or services, and/or percentages. The specification may bedisplayed in other manners as well.

FIGS. 6A-K illustrate exemplary interfaces on computing devices,consistent with disclosed embodiments. As shown in FIG. 6A, in someembodiments the interfaces may be display in a mobile application 602executed on the computing device 600. The interfaces may be displayed inother manners as well.

An interface may be provided through which a user may register with agroup payment system, as shown in FIG. 6A. The interface may includefields into which a user may input registration information, such as auser name 604 and an email address 606. Other registration informationis possible as well.

Additionally, the interface may permit the user to select a manner ofpayment 608. The user may provide payment in many manners. In someembodiments, for example, the user may provide payment through a creditcard or bank account. To this end, the group payment system and/or thecomputing device may be configured to communicate with one or more FSPsystems, such as FSP system 116 described above. Alternatively oradditionally, the user may provide payment through a third-party paymentapplication. To this end, the group payment system and/or the computingdevice may be configured to communicate with one or more third-partysystems, such as third-party system(s) 118 described above. Stillalternatively or additionally, in some embodiments the group paymentsystem may itself be configured to provide a manner of payment. To thisend, the group payment system may be configured to provide the facilityof one or both of an FSP system and a third-party system. Other mannersof payment are possible as well.

After registering with the group payment system, the user may wish tocreate a group payment event. An interface through which a user maycreate a group payment event is shown in FIG. 6B. In some embodiments,the interface may include fields in which a user may input group paymentevent information, such as an event name 610, an event date 612, and/oran expected contribution 614. The expected contribution may be input as,for example, dollar amounts, goods or services, and/or percentages. Anyof the event name 610, event date 612, and expected contribution 6′4 maybe input manually and/or selected from suggestions (e.g., of dates,etc.) and/or a list (e.g., of contributions, etc.). Other contributionsare possible as well.

As shown, in some embodiments the interface for creating the grouppayment may include a guest selection option 616 through which the usermay invite guests. Upon selection of guest selection option 616, a guestselection interface may be displayed, as shown in FIG. 6C. The user mayselect guests from the guest selection interface by, for example,selecting guest icons 618 indicating guests. While the guest icons 618are shown as images, in some embodiments guest icons 618 may be providedas text, telephone numbers, or in another manner. Additionally, whilefour guest icons 618 are shown, in some embodiments more or fewer guesticons 618 may be included in the interface. In some embodiments, a usermay search for guests among, for instance, the user's contacts stored onthe computing device and/or through social media accounts of the userhaving “friend lists,” “connections,” etc., stored, for example, by athird-party system 118. A user may select guests in other manners aswell.

In some embodiments, a user may select an “add new guest” option 620 toadd to the group payment event a guest who has not registered with thegroup payment system. In some embodiments, upon selection of “add newguest” option 620, the computing device may provide to the group paymentsystem identifying information of the new guest (e.g., phone number,physical address, e-mail address, social network profile, etc.), and thegroup payment system may send to a computing device (via, e.g., the newguest phone number, e-mail address, etc.) associated with the new guestan invitation (e.g., a hyperlink, API, etc.) to join the group paymentevent. Alternatively, in some embodiments, upon selection of “add newguest” option 620, the computing device may send to a computing deviceassociated with the new guest an invitation to join the group paymentevent.

An example invitation 622 to join the group payment event is shown inFIG. 6D. In some embodiments, invitation 622 may be displayed in aninterface on computing device 620 associated with the new guest. Asshown, the invitation may include a “join” option 624. “Join” option 624may be, for example, a link (e.g., hyperlink, API, etc.). In someembodiments, upon selecting the link, the new guest may provide to thegroup payment system a request to join the group payment event. In someembodiments, upon selecting the link, the new guest may be prompted toregister and/or provide information to the group payment system.Invitation 622 may take other forms as well.

An example interface for a group payment event is shown in FIG. 6E. Asshown, the interface may indicate an event name 626 and an expectedcontribution for the group payment event. In some embodiments, as shown,the interface may further indicate guests who have contributed to thegroup payment event, as well as the values of the contributions. Theinterface may further include both a “contribute” option 628 and a“discuss” option 630.

By selecting of “contribute” option 628, a user may make a contributionto the group payment event. For example, in some embodiments, uponselection of “contribute” option 628, the user may select one or both ofa contribution amount and a manner of payment. For example, the user mayselect to make a contribution in the amount of the expected contributionusing a bank account provided by the user during registration. Otherexamples are possible as well.

By selecting “discuss” option 630, a user may participate in adiscussion among guests of the group payment event, as shown in FIG. 6F.The discussion may include any number of messages 634. In someembodiments, the messages may pertain to the financial contributions ofthe guests. The messages need not pertain to the financialcontributions, however, or even the group payment event. Any messagesare possible.

An example interface including a specification of financialcontributions 636 by guests is shown in FIG. 6G. In some embodiments,specification of the financial contributions 636 may include dollaramounts of each guests target contributions. Alternatively oradditionally, in some embodiments, specification of the financialcontributions 636 may include a graphical indication 638 of each guest'starget and/or actual financial contribution. The specification of thefinancial contributions 636 may take other forms as well.

In some embodiments, the financial contributions may be revised, forinstance, as a result of discussion in the messages. In theseembodiments, a guest may, through a computing device, electronicallytransmit to the group payment server a specification of revisedfinancial contributions. In response to receiving the specification ofthe revised financial contributions, the group payment system may modifythe interface to replace specification of the financial contributions636 with the specification of the revised financial contributions, andthe computing devices may display the modified interfaces. In someembodiments, the group payment system may poll or otherwise consult theguests of the group payment system before replacing specification of thefinancial contributions 636 with the specification of the revisedfinancial contributions. Alternatively or additionally, only a creatorof the group payment event may replace specification of the financialcontributions 636 with the specification of the revised financialcontributions. The replacement may be done in other manners as well.

An example interface through which transaction information for purchasesrelated to the group payment event may be displayed is shown in FIG. 6H.In some embodiments, the transaction information may be received by thegroup payment system from computing devices associated with guests ofthe group payment event. For example, a guest may enter (e.g., manually,by scanning a receipt, etc.) transaction information for a purchaserelated to the group payment event into a computing device, and thecomputing device may provide the transaction information to the grouppayment system. The group payment system may modify the interface todisplay the transaction information. As another example, the transactioninformation may be received by the computing device from an FSP system,such as FSP system 116. In response to the user confirming that thetransaction information is for a purchase related to the group paymentevent, the computing device or the FSP system may provide thetransaction information to the group payment system, and the grouppayment system may modify the interface to display the transactioninformation. As still another example, the transaction information maybe received by the group payment system from the FSP system withoutinteraction by the user or computing device. The transaction informationmay be received in other manners as well.

In some embodiments, in response to receiving the transactioninformation, the group payment server may determine updated financialcontributions for the guests. For example, a guest's actual financialcontribution 644 may be increased to reflect a purchase made by theguest, as shown in FIG. 6I. As another example, other guests' targetfinancial contributions may be increased to reflect the purchase made bythe guest. Other examples are possible as well. In general, theinterface may be modified to display the updated financialcontributions.

Returning to FIG. 6H, the interface may further provide a “settle up”option 642, through which guests of the group payment event mayreconcile their financial contributions to the group payment event. Anexample interface for settling a group payment event is shown in FIG.6J. In some embodiments, guest-to-guest transactions 646 may beprovided. Guest-to-guest transactions 646 may, for example, reflect theminimum number of financial exchanges through which the group paymentevent may be settled. Other guest-to-guest transactions 646 are possibleas well.

In some embodiments, the interface may include a “pay now” option 648for guest-to-guest transaction(s) 646 in which the user owes money toanother guest. By selecting the “pay now” option 648, the user may makea payment to the other guest, e.g., in any of the payment mannersdescribed above. Alternatively or additionally, in some embodiments theinterface may include a “request now” option 650 for guest-to-guesttransaction(s) 646 in which the user is owed money by another guest. Byselecting “request now” option 650, the user may request a payment fromthe other guest, e.g., in any of the payment manners described above. Insome embodiments, the group payment system may be configured tofacilitate and/or provide notifications regarding such payments andrequests for payment.

When a user makes a payment to or receives a payment from another guest,a notification of the payment may be sent to the group payment system.In response to receiving the notification of payment, the group paymentserver may determine updated financial contributions. For example, ifthe user has made a payment to another guest, the user's financialcontribution may be increased and the other guest's financialcontribution may be decreased. As another example, if the user hasreceived a payment from another guest, the user's financial contributionmay be decreased and the other guest's financial contribution may beincreased. The updated financial contributions may be determined inother manners as well.

The group payment server may modify the interface to display the updatedfinancial contributions, as shown in FIG. 6K. In some embodiments, asshown, the updated financial contributions may be displayed by modifyingthe actual financial contributions 652. The updated financialcontributions may be displayed in other manners as well.

While several example interfaces are shown in FIGS. 6A-K, it will beunderstood that the interfaces shown are merely examples and that otherinterfaces are possible as well.

Further, while the foregoing examples focused on a group payment eventoccurring in the future, it will be understood that similar grouppayment systems, computing devices, processes, and interfaces may beused to facilitate group payment of an event that occurred in the pastas well. For example, a group payment event may be created reflecting ameal shared by guests at a restaurant, and the financial contributions,transaction information, and payments associated with the meal may beprovided, displayed, and settled as described above. Other examples arepossible as well.

Additionally, while the foregoing examples focused on mobile computingdevices executing a mobile application, it will be understood thatsimilar group payment systems, processes, and interfaces may be used tofacilitate group payment with computing devices providing access to aweb platform and email.

In some examples, some or all of the logic for the above-describedtechniques may be implemented as a computer program or application or asa plug-in module or subcomponent of another application. The describedtechniques may be varied and are not limited to the examples ordescriptions provided.

Moreover, while illustrative embodiments have been described herein, thescope thereof includes any and all embodiments having equivalentelements, modifications, omissions, combinations (e.g., of aspectsacross various embodiments), adaptations and/or alterations as would beappreciated by those in the art based on the present disclosure. Forexample, the number and orientation of components shown in the exemplarysystems may be modified. Further, with respect to the exemplary methodsillustrated in the attached drawings, the order and sequence of stepsmay be modified, and steps may be added or deleted.

Thus, the foregoing description has been presented for purposes ofillustration only. It is not exhaustive and is not limiting to theprecise forms or embodiments disclosed. Modifications and adaptationswill be apparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. For example,while a financial service provider and merchant have been referred toherein for ease of discussion, it is to be understood that consistentwith disclosed embodiments other entities may provide such services inconjunction with or separate from a financial service provider andmerchant.

The claims are to be interpreted broadly based on the language employedin the claims and not limited to examples described in the presentspecification, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods may be modified in anymanner, including by reordering steps and/or inserting or deletingsteps.

Furthermore, although aspects of the disclosed embodiments are describedas being associated with data stored in memory and other tangiblecomputer-readable storage mediums, one skilled in the art willappreciate that these aspects can also be stored on and executed frommany types of tangible computer-readable media, such as secondarystorage devices, like hard disks, floppy disks, or CD-ROM, or otherforms of RAM or ROM. Accordingly, the disclosed embodiments are notlimited to the above described examples, but instead is defined by theappended claims in light of their full scope of equivalents.

1-20. (canceled)
 21. A group payment system, comprising: a communicationdevice configured to communicate with a plurality of guest computingdevices, wherein each guest computing device is associated with at leastone guest; a memory storing instructions; and a processor configured toexecute the instructions to perform operations comprising: receiving arequest to create a group payment event including a list of guests;receiving, in response to creating the group payment event, a request toinvite at least one additional guest to the group payment event;sending, via the communication device, an invitation to the invitedguest; adding, in response to the invited guest accepting theinvitation, the invited guest to the group payment event; providing agroup payment interface to the guest computing devices; receiving, viathe group payment interface, a specification of financial contributionfrom one of the guests; modifying the group payment interface to reflectthe financial contribution from the one guest; providing the modifiedgroup payment interface to the guest computing device.
 22. The grouppayment system of claim 21, wherein the group payment interfacecomprises instructions for displaying a shared graphical user interfaceon a display of the guest computing devices.
 23. The group paymentsystem of claim 21, wherein the operations further comprise: receivingtransaction information for a purchase related to the group paymentevent; modifying the group payment interface to reflect the receivedtransaction information; and providing the modified group paymentinterface to the guest computing devices.
 24. The group payment systemof claim 23, further comprising: determining updated financialcontributions based on the received transaction information; andmodifying the group payment interface with instructions to display theupdated financial contributions.
 25. The group payment system of claim23, wherein receiving the transaction information comprises receivingthe transaction information from one of the guest computing devices. 26.The group payment system of claim 23, wherein receiving the transactioninformation further comprises receiving the transaction information froma financial service provider.
 27. The group payment system of claim 21,further comprising: receiving a notification of payment from a firstguest to a second guest; updating the financial contributions of thefirst guest and second guest based on the received notification ofpayment; modifying the group payment interface with instructions todisplay the updated financial contributions of the first guest andsecond guest; and providing the modified group payment interface to theguest computing devices.
 28. The group payment system of claim 21,further comprising: receiving, from one of the guest computing devices,a message associated with the group payment event; modifying the grouppayment interface with instructions to display the message; andproviding the modified group payment interface to the guest computingdevices.
 29. The group payment system of claim 21, wherein the grouppayment interface comprises instructions for displaying a graphicalindication of the financial contributions of each against a targetfinancial contribution.
 30. The group payment system of claim 21,wherein the communication device communicates with the plurality ofguest computing devices over a network.
 31. A method, comprising:receiving a request to create a group payment event including a list ofguests; receiving, in response to creating the group payment event, arequest to invite at least one additional guest to the group paymentevent; sending, via a communication device, an invitation to the invitedguest; adding, in response to the invited guest accepting theinvitation, the invited guest to the group payment event; providing agroup payment interface to a plurality of guest computing devices,wherein each guest computing device is associated with at least oneguest; receiving, via the group payment interface, a specification offinancial contribution from one of the guests; modifying the grouppayment interface to reflect the financial contribution from the oneguest; providing the modified group payment interface to the guestcomputing devices.
 32. The method of claim 31, wherein the group paymentinterface comprises instructions for displaying a shared graphical userinterface on a display of the guest computing devices.
 33. The method ofclaim 31, wherein the operations further comprise: receiving transactioninformation for a purchase related to the group payment event; modifyingthe group payment interface to reflect the received transactioninformation; and providing the modified group payment interface to theguest computing devices.
 34. The method of claim 33, further comprising:determining updated financial contributions based on the receivedtransaction information; and modifying the group payment interface withinstructions to display the updated financial contributions.
 35. Themethod of claim 33, wherein receiving the transaction informationcomprises receiving the transaction information from one of the guestcomputing devices.
 36. The method of claim 33, wherein receiving thetransaction information further comprises receiving the transactioninformation from a financial service provider.
 37. The method of claim31, further comprising: receiving a notification of payment from a firstguest to a second guest; updating the financial contributions of thefirst guest and second guest based on the received notification ofpayment; modifying the group payment interface with instructions todisplay the updated financial contributions of the first guest andsecond guest; and providing the modified group payment interface to thecomputing devices associated with each of the guests.
 38. The method ofclaim 31, further comprising: receiving, from one of the guest computingdevices, a message associated with the group payment event; modifyingthe group payment interface with instructions to display the message;and providing the modified group payment interface to the guestcomputing devices.
 39. The method of claim 31, wherein the group paymentinterface comprises instructions for displaying a graphical indicationof the financial contributions of each against a target financialcontribution.
 40. The group payment system of claim 31, wherein thecommunication device communicates with the plurality of guest computingdevices over a network.